Security aware email server

ABSTRACT

A security aware email server and a method of managing incoming email are described. The server includes a memory device configured to store rules, instructions, and user preferences. The processor makes a determination of whether a sender of an incoming email used a secure or unsecure sending network to send the email and determines an action to take with the email based on the determination and the user preferences.

DOMESTIC BENEFIT/NATIONAL STAGE INFORMATION

This application is a continuation of U.S. application Ser. No.14/840,106 filed Aug. 31, 2015, the disclosure of which is incorporatedby reference herein in its entirety.

BACKGROUND

The present invention relates to electronic mail (email), and morespecifically, to a security aware email server.

Email is increasingly used for both personal and professionalcommunication. With the increased use of mobile devices for sending andreceiving email, emails may be sent from almost anywhere and may bereceived almost anywhere. While they increase the convenience in usingemail as a form of communication, mobile platforms may also raisesecurity concerns. This is because a sender of email may not have used ahome computer with a password-protected network, for example, or asecure enterprise network at the office. Instead, the email sender mayhave been connected to the internet through a public wireless network(e.g., WiFi) at a coffee shop, airport, or other location.

SUMMARY

According to one embodiment of the present invention, a security awareemail server includes a memory device configured to store rules,instructions, and user preferences; and a processor configured to make adetermination of whether a sender of an incoming email used a secure orunsecure sending network to send the email and to determine an action totake with the email based on the determination and the user preferences.

According to another embodiment, a non-transitory computer programproduct stores instructions which, when processed by a processor, causethe processor to implement a method of managing incoming email at anemail server. The method includes receiving the email with informationappended thereto, the information including an indication of a locationof a sender of the email and security status of a network used to sendthe email; determining whether the sending network is secure orunsecure; and determining an action to take with the email based on thedetermining whether the sending network is secure or unsecure and onuser preferences.

According to yet another embodiment, a method of managing incoming emailat an email server includes receiving the email with informationappended thereto, the information including an indication of a locationof a sender of the email and security status of a sending network usedto send the email; determining, using a processor, whether the sendingnetwork is secure or unsecure; and determining, using the processor, anaction to take with the email based on the determining whether thesending network is secure or unsecure and on user preferences.

Additional features and advantages are realized through the techniquesof the present invention. Other embodiments and aspects of the inventionare described in detail herein and are considered a part of the claimedinvention. For a better understanding of the invention with theadvantages and the features, refer to the description and to thedrawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The subject matter which is regarded as the invention is particularlypointed out and distinctly claimed in the claims at the conclusion ofthe specification. The forgoing and other features, and advantages ofthe invention are apparent from the following detailed description takenin conjunction with the accompanying drawings in which:

FIG. 1 is a block diagram illustrating an email system according toembodiments;

FIG. 2 is a process flow of a general method of managing incoming mailat a receiving server according to embodiments;

FIG. 3 details processes shown in FIG. 2 according to embodiments; and

FIG. 4 details processes shown in FIG. 2 according to anotherembodiment.

DETAILED DESCRIPTION

As noted above, the use of mobile platforms (e.g., tablets, smartphones, laptop computers) and wide availability of publicly accessiblenetworks has resulted in many emails being sent from unsecure networks.The location of an email sender is not necessarily dispositive indetermining security of the network. That is, a user at a coffee shopmay use a password-protected mobile hotspot or a personal cellularnetwork to send emails or may use the public unsecure network to sendemails. The sender's email server may append information to the emailthat facilitates determination by the recipient email server of whetherthe email was sent from a secure or unsecure network. When an unsecurenetwork is used to send email, the email may be embedded with malware inattachments and other forms. Embodiments of the systems and methodsdetailed herein relate to various actions that the receiving emailserver may take to protect the email recipient based on a determinationof the type of network used to send the email.

FIG. 1 is a block diagram illustrating an email system according toembodiments detailed below. Any number of users using devices 110 may beboth senders and recipients of email. As noted above, each device 110may be a computer, laptop, tablet, smartphone, or other computing devicethat facilitates network communication. Each device 110 includes one ormore memory devices 112, one or more processors 115, and othercomponents known to facilitate the processing and communication ofinformation. Each user device 110 accesses an email server 130 in orderto send or to receive the email. The server 130 may manage otherinformation in addition to email or may be a dedicated email server.Each server 130 also includes one or more memory devices 122 and one ormore processors 125 among other components that facilitate theprocessing and communication discussed below according to variousembodiments. The memory device 122 may store default rules as well asthe user preferences discussed below. The processor 125 determines oneor more of the actions to take with a received email that are detailedbelow. The device 110 connects to the server 130 via a network 120. Thenetwork 120 used by a given device 110 to access the email server 120may be secure or unsecure. Any device 110 may send or receive email, anynetwork 120 may be used to connect to a server 120 for the purpose ofsending or receiving email, and any server 120 may be a sending orreceiving server. Further, in reality, the same server 130 may manageboth sending and receiving of the same email to the same or differentdevices 110. However, for explanatory purposes, when discussing a givenemail, the labels “sending” or “receiving” may be added to a device 110,network 120, and server 130 (e.g., sending device 110, receiving server130) herein.

FIG. 2 is a process flow of a general method of managing incoming mailat a receiving server 130 according to embodiments further detailedbelow. As noted above with reference to FIG. 1, a sender or recipient ofemail uses a computing device 110 (e.g., computer, laptop, smart phone,tablet) that is connected (e.g., wirelessly, via Ethernet) through anetwork 120 to an email server 130 that manages that message. Thenetwork connection that the sending or receiving device 110 has with theserver 130 may be secure (e.g., a personal, password-protectedconnection) or unsecured (e.g., public WiFi). The server 130 used by theemail sending device 110 and receiving device 110 may be the same oreach may have a different network connection to the server 130. At block210, receiving an email message is from a sender's server 130 at therecipient's email server 130. As noted above, the sender and recipientservers 130 may be the same one. At block 220, obtaining appendedinformation and, optionally, conditions at the receiving server 130includes obtaining information that indicates the security level of thenetwork 120 used to connect the sender device 110 to the sending server130. The information may include not only the location of the emailsender (sending device 110) but also the security features of thesender's network 120 or location information of the sending device 110that helps to determine if the sending server 130 is secure or not, forexample. When conditions are included with the email, these conditionsmay indicate when the receiving server 130 can release the email to therecipient's device 110. That is, the sender of the email may specifyconditions required for the receiving server 130 or receiving device110. For example, the sender of the email may specify that the recipientmay not open the email using a public unsecured network 120. At block230, determining sender network 120 status includes using the appendedinformation to determine if the email was sent via a secure or unsecurenetwork 120. At block 240, determining the recipient network 120 statusis an optional process performed according to any conditions includedwith the received email. The receiving server 130 determines whether therecipient is part of a secure or unsecure network 120. At block 250,obtaining user preferences is used in conjunction with other informationin determining action(s) to be taken by the receiving server 130 atblock 260. The user preferences may include locations or networks 120that the recipient wishes to designate as secure or unsecure. Thesepreferences may override the determination at block 230 in somesituations or may cause the receiving server 130 to ask the recipientregarding an override. Specific embodiments and additional details areprovided below.

FIG. 3 details processes shown in FIG. 2 according to embodiments. Afterdetermining the sender network 120 status at block 230 (based onobtaining appended information at block 220 (FIG. 2)), a check is doneof whether the sender network 120 is secure or not at 310. In additionto the answer to block 310, user preferences are also used based onobtaining user preferences at block 250. Determining the action(s) 260of the receiving server 130 includes determining among two sets ofactions 260-1 and 260-2 based on the status of the sender network 120,as shown in FIG. 3. When the sender's network 120 is secure (i.e., thesending device 110 used a secure network 120 to connect to the sendingserver 130), determining the action(s) 260-1 includes forwarding theemail to the recipient device 110, indicating the sender network 120status or other information to the email recipient device 110, or acombination of the two. Other information provided to the emailrecipient may include the location of the email sender, for example.Whether and which information is included along with the email itself aspart of the actions 260-1 may be based on defaults set in the receivingserver 130 or on user preferences (obtained at block 250). Both thereceiving server 130 and user preferences may address the same action(e.g., whether to indicate the sender's network 120 status). In thiscase, the user preferences may overrule default options in the receivingserver 130. In alternate embodiments, rules may be established in theservers as to which default options may be overruled by userpreferences.

When the sender network 120 is unsecure, determining the actions 260-2includes performing one or a combination of the actions shown in FIG. 3and discussed herein. User preferences (determined at block 250) play apart in determining which actions are performed. The receiving device110 may be provided with information (e.g., sender network 120 status,sender location) and then given a choice as to whether to retrieve theemail from the receiving server 130 or not. The user preferences mayspecify not only whether the choice is to be given by the receivingserver 130 but also which information to provide. Alternately oradditionally, based on the content of the email (e.g., text, hypertextmarkup language (HTML) elements, attachments), only a portion of theemail may be forwarded to the recipient's device 110 when the sendernetwork 120 is determined to be unsecure. For example, only text may beforwarded from the receiving server 130 to the receiving device 110.This option may be combined with the previous option according to userpreferences. That is, for example, the receiving server 130 may releaseonly text and, additionally, may send an inquiry to the recipient(receiving device 110) as to whether the remaining content should bereleased or not.

As yet another alternative, the email may be cleansed by the receivingserver 130. Thus, the receiving server 130 may perform a search formalware, viruses, and uniform resource locator (URL) links created withthe scripting language php and address any identified issues by knowntechniques before sending the email to the recipient. Again, userpreferences may dictate not only this process being performed but alsoany additional information provided to the user along with the cleansedemail. In yet another embodiment, the receiving server 130 may segregatethe email received from a sending device 110 that used an unsecurenetwork 120 in a secondary server. This action by the receiving server130, based on server settings, may be combined with other options notedabove. That is, once the receiving server 130 has segregated the emailreceived by a sender using an unsecure network 120, the receiving server130 may then provide information and a choice of whether to open theemail to the recipient or may cleanse the email, or forward only aportion of the email. Segregating the email facilitates protecting thereceiving server 130. If the user chooses to open the email andconsequently releases a virus or other malware, the receiving server 130and other devices 110 connected to the server 130 may be unaffectedwhile the issue is dealt with in the segregated server 130. Yet anotheraction the receiving server 130 (alone or based on user preferences) maydetermine to take is requesting information from other recipients'servers 130. That is, when the receiving server 130 determines (at block230) that email was received from a device 110 using an unsecure network120, the receiving server 130 may transmit an inquiry to other servers130 associated with other recipients of the same email. It should beunderstood that all recipients of a given email may be accessing thesame server 130. In this case, the disposition of the email is known tothe server 130. When at least one other recipient of the email isaccessing a different server 130, the receiving server 130 may requestinformation to help assess whether the email may safely be opened. Theinformation may include the result of any cleansing process performed bythe other server 130 or the result of a user device 110 opening theemail through the other server 130, for example. The receiving server130 may forward this information to the receiving device 110.

FIG. 4 details processes shown in FIG. 2 according to anotherembodiment. FIG. 4 details the processes relating to a conditionincluded with information from the sending server 130. As noted above,the condition may dictate that the recipient may not open the emailunless connected to the receiving server 130 through a secure network120, for example. When such a condition is received (at block 220), thereceiving server 130 determines whether the recipient network 120 status(the network 120 connecting the receiving device 110 to itself) issecure (at block 240). At 410, a check is performed of whether therecipient network 120 is secure. When the receiving network 120 is notsecure, the condition received from the sender may be followed. Forexample, the condition may dictate that the email be held and processedagain after the recipient has changed the network 120 being used toaccess the receiving server 130 (e.g., recipient moves from public WiFito home network). When the receiving network 120 is secure, then therecipients preferences (obtained at block 250) are considered based on adetermination of the sender's network 120 status (at block 230) usingthe information received (at block 220). That is, the receiving server130 may not forward an email even when, according to the condition fromthe sender, the receiving network 120 is secure. Instead, when a check(at 420) indicates that the sending network 120 is not secure, then thereceiving server 130 rules and user preferences may dictate whether theemail is partially sent, cleansed, reported with an option to open, orany other option available (at block 260-2) per the discussion withreference to FIG. 3. When a check (at 420) indicates that the sendingnetwork 120 is secure (and the sender's condition has been determined tobe met per 410), then the email may be forwarded to the receiving device110 and may include additional information as discussed with referenceto FIG. 3 (block 260-1).

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of onemore other features, integers, steps, operations, element components,and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the present invention has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the invention. Theembodiment was chosen and described in order to best explain theprinciples of the invention and the practical application, and to enableothers of ordinary skill in the art to understand the invention forvarious embodiments with various modifications as are suited to theparticular use contemplated.

The flow diagrams depicted herein are just one example. There may bemany variations to this diagram or the steps (or operations) describedtherein without departing from the spirit of the invention. Forinstance, the steps may be performed in a differing order or steps maybe added, deleted or modified. All of these variations are considered apart of the claimed invention.

While the preferred embodiment to the invention had been described, itwill be understood that those skilled in the art, both now and in thefuture, may make various improvements and enhancements which fall withinthe scope of the claims which follow. These claims should be construedto maintain the proper protection for the invention first described.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the describedembodiments. The terminology used herein was chosen to best explain theprinciples of the embodiments, the practical application or technicalimprovement over technologies found in the marketplace, or to enableothers of ordinary skill in the art to understand the embodimentsdisclosed herein.

What is claimed is:
 1. A method of managing incoming email at an emailserver, the method comprising: receiving, via a receiving network, theemail with information appended thereto, the information including anindication of a location of a sender of the email, a security status ofa sending network used to send the email, and a condition that thereceiving network must be secure, the condition including a securitylevel of the sending network used to connect the sender device to thesending network and security features of the sender network;determining, using a processor, whether the sending network is secure orunsecure based on the information appended to the email; determining,using the processor, whether the receiving network is secure orunsecure; forwarding the email to a recipient of the email based on thesending network and the receiving network being secure and based on userpreferences, wherein the user preferences indicate whether to retrievethe email from the receiving network or not; forwarding a portion of theemail, segregating the email in a secondary server, or cleansing theemail based on searching for malware, viruses, and uniform resourcelocator (URL) links created with the scripting language php prior toforwarding the email based on the sending network being unsecure and thereceiving network being secure, wherein the receiving network sends aninquiry to the recipient as to whether remaining content should bereleased or not; and storing the email and forwarding the email to therecipient only when the recipient uses a secure receiving network basedon the sending network being secure and the receiving network beingunsecure.